-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Code to 1.94.0 #7026
Update Code to 1.94.0 #7026
Conversation
- Fixes coder#7018
- vscode: Seems like you are using `yarn` which is not supported in this repo any more, please use `npm i` instead.
Notes: --- lib/vscode/src/vs/platform/extensionManagement/node/extensionDownloader.ts
+++ lib/vscode/src/vs/platform/extensionManagement/node/extensionDownloader.ts
@@ -114,7 +114,10 @@ export class ExtensionsDownloader extend
return false;
}
+ return false
+ // @ts-expect-error
const value = this.configurationService.getValue('extensions.verifySignature');
+ // @ts-expect-error
return isBoolean(value) ? value : true;
} 👉 Code does not exist any more --- lib/vscode/src/vs/workbench/contrib/remote/browser/remoteExplorer.ts
+++ lib/vscode/src/vs/workbench/contrib/remote/browser/remoteExplorer.ts
@@ -77,7 +77,7 @@ export class ForwardedPortsView extends
private async enableForwardedPortsView() {
this.contextKeyListener.clear();
- const viewEnabled: boolean = !!forwardedPortsViewEnabled.getValue(this.contextKeyService);
+ const viewEnabled: boolean = true;
if (viewEnabled) {
const viewContainer = await this.getViewContainer(); ℹ️ Also --- lib/vscode/src/vs/workbench/workbench.web.main.ts
+++ lib/vscode/src/vs/workbench/workbench.web.main.ts
@@ -52,7 +52,7 @@ import 'vs/workbench/services/dialogs/br
import 'vs/workbench/services/host/browser/browserHostService';
import 'vs/workbench/services/lifecycle/browser/lifecycleService';
import 'vs/workbench/services/clipboard/browser/clipboardService';
-import 'vs/workbench/services/localization/browser/localeService';
+import 'vs/workbench/services/localization/electron-sandbox/localeService';
import 'vs/workbench/services/path/browser/pathService';
import 'vs/workbench/services/themes/browser/browserHostColorSchemeService';
import 'vs/workbench/services/encryption/browser/encryptionService';
@@ -118,8 +118,9 @@ registerSingleton(ILanguagePackService,
// Logs
import 'vs/workbench/contrib/logs/browser/logs.contribution';
-// Localization
-import 'vs/workbench/contrib/localization/browser/localization.contribution';
+// Localization. This does not actually import anything specific to Electron so
+// it should be safe.
+import 'vs/workbench/contrib/localization/electron-sandbox/localization.contribution';
// Performance
import 'vs/workbench/contrib/performance/browser/performance.web.contribution'; 👉 Code does not exist any more |
@code-asher Please review and migrate the CI from Thank you. Cross reference: |
@code-asher
|
VS Code switched to npm?? Great news. I will try to get to this today. |
Yes. |
24905b4
to
bce606d
Compare
This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment.
bce606d
to
f5c121a
Compare
This was complaining on every unit test.
b9e4e95
to
cdc013f
Compare
I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit.
I was getting oom when running the unit tests...updating seems to work.
cdc013f
to
20f6fce
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7026 +/- ##
=======================================
Coverage ? 72.59%
=======================================
Files ? 31
Lines ? 1905
Branches ? 412
=======================================
Hits ? 1383
Misses ? 442
Partials ? 80
Continue to review full report in Codecov by Sentry.
|
@code-asher |
The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive.
@code-asher |
Was not able to get back to this last week but am aiming to get it sorted today or maybe tomorrow. |
This appears to be conflicting with the root dependencies.
npm does not let you run binaries like yarn does, as far as I know.
The entrypoint having been rewritten in ESM is making things really difficult, I started converting us to ESM but it is a nightmare. Think tomorrow I am going to break out VS Code into a separate process and communicate via IPC rather than importing it directly in the same process, should completely isolate us from any changes VS Code makes like this, and is the way it really should have been done in the first place. |
Sounds like a major change. I will do more extensive testing with the release candidate, then. |
So, I got most of that done last night but, as you guessed it is getting pretty complicated. I still think it is probably the right move long-term but for this release I think I will go with a simpler fix and just rewrite |
Actually I can just copy the old |
Go for it. |
d303968
to
4744383
Compare
4744383
to
e4ceeab
Compare
1ba9b15
to
1c40db2
Compare
1c40db2
to
7b1ddc1
Compare
Fixes the icons and fetching modules from the browser when behind a reverse proxy.
2104261
to
99a8db2
Compare
* Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
Ping @code-asher: Functionality [modified by patches] tested and found to work:
Workspaces and Jupyter Notebooks also work fine:
ℹ️ Because of issue #7042, these are not installed as built-in extensions. Safari is unable to render the font's (MesloLGS NF) glyphs and symbols properly: ℹ️ No problem with Firefox. |
I was able to reproduce the Terminal font issue in Codespaces and opened an issue: |
Sorry for the delay, I was out last week. Thank you for opening that upstream! Hmm that extension installation issue sounds like a release blocker. |
No worries.
👍
Yes. |
Fixes #7018
yarn -> npm
yarn
which is not supported in this repo any more, please usenpm i
instead.